-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Abstract Ignition operations in a single file #3248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
this is too big a commit to review. can you break it apart into new functions and then moving existing code to it. also ignConfig isn't a great name. |
Okay, will do
It can be addressed later.
That can be done in approximately 4.6 time, when RHCOS switches to Ignition v3. OKD installer would like to do that earlier. |
16f9110 to
c785f43
Compare
|
/cc @openshift/openshift-team-mco-maintainers |
pkg/asset/ignition/ignition_v2.go
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opened a PR a month ago to support Spec 2.4 in the provider: hashicorp/terraform-provider-ignition#67
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this may not be needed after all. If you don't have to use 2.4 everywhere, I'd say let's not in order to keep changes to a mininum.
|
MCO should probably be updated to natively use Ignition Spec 2.4 before this can go in? |
|
openshift/machine-config-operator#1543 adds support for Spec 2.4, |
c785f43 to
08305f9
Compare
0d3c284 to
3de649f
Compare
|
ovirt flaked, workers didn't join on openstack /retest |
|
/hold Openstack workers don't join the cluster |
|
Imagestream import issues |
|
/retest |
1383b6f to
60fa219
Compare
|
/retest |
|
/hold cancel All issues resolved, PTAL |
60fa219 to
f4fb1b6
Compare
|
/test e2e-metal-ipi |
1 similar comment
|
/test e2e-metal-ipi |
f4fb1b6 to
c5ede55
Compare
|
/retest |
c5ede55 to
f9e7abd
Compare
f9e7abd to
4fc5d48
Compare
|
@vrutkovs do you mind updating this PR once again? Spec 3 support has now merged into MCO, the migration could happen be done any time now. |
We still need RHCOS to run Ign3 for tests to pass |
This file would contain functions which create or change Ignition files, importing a version of github.com/coreos/ignition
…nal MachineConfigs. Functions from pkg/asset/ignition/node.go are no longer used, so it is removed. `runtime.Extension` is used to be compatible with different Ignition versions
4fc5d48 to
e333587
Compare
|
/retest |
|
@vrutkovs: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Superceded by #3871 |
This PR moves all functions which create or modify Ignition in a single file and abstract Ignition config in
IgnConfig.The change would enable us to replace Ignition v2 implementation with Ignition v3 using build tags (or any other way on compile-time).
This ensures machineconfigs are created with Ignition 2.2.0 and Openstack shim is created using Ignition v2.4.0.
/cc @LorbusChris @cgwalters @openshift/installer